SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 45139: Unable to connect to the SAS® Metadata Server when using direct authentication to a load-balanced LDAP server using SSL

DetailsHotfixAboutRate It

If the SAS® Metadata Server is configured for direct authentication to a Lightweight Directory Access Protocol (LDAP) over Secure Sockets Layer (SSL), and the LDAPS server is configured for load–balancing, you might receive the following errors when attempting to log into the SAS Metadata Server:

ERROR: Invalid credentials ERROR: Access denied. ERROR: Unable to contact the LDAP server. ERROR: Possible cause: Server certificate not found, port not SSL enabled ERROR: LDAP SSL Message ldapsNegotiate() failed -2139099117

In this scenario, the value of the LDAP_HOST in the SAS Metadata Server's configuration references the LDAP server load balancer. When an authentication request is sent to this load–balancing server, it forwards the request to one of the LDAP servers in the cluster. This "real" LDAP server answers with its own certificate, which contains references to its own server name.

The errors occur because the SAS Metadata Server compares the host name in the certficate with the name of the host defined in the LDAP_HOST configuration option and the values do not match.

Click the Hot Fix tab in this note to access the hot fix for this issue.

NOTE: In addtion to installing the hot fix, you must also create the NOSSLNAMECHECK environment variable to prevent the errors. You can create the environment variable by adding the following command to your sasv9.cfg file:

-set NOSSLNAMECHECK 1

Another option, if you are launching SAS® from a script, is to define the environment variable in the script prior to the SAS command:

export NOSSLNAMECHECK=1


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Metadata Serverz/OS9.39.3_M19.3 TS1M09.3 TS1M2
Microsoft® Windows® for x649.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition9.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition9.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows Server 2003 Standard Edition9.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows Server 2003 for x649.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows Server 20089.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows Server 2008 for x649.39.3_M19.3 TS1M09.3 TS1M2
Microsoft Windows XP Professional9.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Enterprise 32 bit9.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Enterprise x649.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Home Premium 32 bit9.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Home Premium x649.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Professional 32 bit9.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Professional x649.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Ultimate 32 bit9.39.3_M19.3 TS1M09.3 TS1M2
Windows 7 Ultimate x649.39.3_M19.3 TS1M09.3 TS1M2
Windows Vista9.39.3_M19.3 TS1M09.3 TS1M2
Windows Vista for x649.39.3_M19.3 TS1M09.3 TS1M2
64-bit Enabled AIX9.39.3_M19.3 TS1M09.3 TS1M2
64-bit Enabled HP-UX9.39.3_M19.3 TS1M09.3 TS1M2
64-bit Enabled Solaris9.39.3_M19.3 TS1M09.3 TS1M2
HP-UX IPF9.39.3_M19.3 TS1M09.3 TS1M2
Linux9.39.3_M19.3 TS1M09.3 TS1M2
Linux for x649.39.3_M19.3 TS1M09.3 TS1M2
Solaris for x649.39.3_M19.3 TS1M09.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.